Systems and methods of making a call

ABSTRACT

Systems and methods of making calls are provided. A particular method includes receiving input indicating a destination address at a mobile communication device. The method also includes determining whether the destination address is of a predetermined type. The method further includes initiating a call to a communication bridge via a mobile communication network when the destination address is of the predetermined type. The method also includes sending an instruction to the communication bridge to initiate a communication connection to the destination address.

CLAIM OF PRIORITY

This application claims priority from U.S. Provisional Patent Application No. 61/014,324, entitled “SYSTEMS AND METHODS OF MAKING A CALL”, filed on Dec. 17, 2007, which is incorporated herein by reference in its entirety.

FIELD OF THE DISCLOSURE

The present disclosure is generally related to a making a call.

BACKGROUND

Some individuals and businesses find that mobile communications devices provide desirable features, such as the ability to communicate during travel or when away from access to landline communications. Additionally, some calls made via mobile communication devices can be cheaper or more convenient than calls made via a landline telephone. However, some calls made using a mobile communication device can be more expensive than calls made via a landline and may have more limited features. Hence, there is a need for improved systems and methods of making calls.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of a first embodiment of a system to make a call;

FIG. 2 is a diagram of a second embodiment of a system to make a call;

FIG. 3 is a flow chart of a first embodiment of a method of making a call;

FIG. 4 is a diagram of a first embodiment of a user interface for making a call;

FIG. 5 is a diagram of a second embodiment of a user interface for making a call;

FIG. 6 is a diagram of a third embodiment of a user interface for making a call;

FIG. 7 is a flow chart of a second embodiment of a method of making a call;

FIG. 8 is a flow chart of a third embodiment of a method of making a call; and

FIG. 9 is a flow chart of a fourth embodiment of a method of making a call.

DETAILED DESCRIPTION OF THE DRAWINGS

A system to make a call is disclosed. The system includes an access interface to receive a voice call to a telephony address associated with the access interface. The call is initiated by a mobile communication device in response to an automatic determination at the mobile communication device to route the call via the access interface based on a destination communication address received at the mobile communication device. The system also includes a communication bridge to initiate a communication to the destination communication address and to convert the voice call to an alternate communication protocol for communication to the destination communication address.

In another particular embodiment, a processor-readable medium includes instructions that, when executed by a processor, cause the processor to receive input indicating a destination address. The processor-readable medium also includes instructions that, when executed by the processor, cause the processor to determine whether the destination address is of a predetermined type. The processor-readable medium also includes instructions that, when executed by the processor, cause the processor to initiate a call to a communication bridge via a mobile communication network when the destination address is of the predetermined type. The processor-readable medium further includes instructions that, when executed by the processor, cause the processor to send an instruction to the communication bridge to initiate a communication connection to the destination address.

In another particular embodiment, a mobile communication device includes an input device to receive input indicating a destination communication address. The mobile communication device also includes an address analysis module to determine whether the destination communication address is of a predetermined type. The mobile communication device also includes a call module to initiate a call to a communication bridge when the destination communication address is of the predetermined type and to send an instruction to the communication bridge to initiate a communication connection to the destination communication address.

In another particular embodiment, a method of making a call is disclosed. The method includes receiving input indicating a destination address at a mobile communication device. The method also includes determining whether the destination address is of a predetermined type. The method further includes initiating a call to a communication bridge via a mobile communication network when the destination address is of the predetermined type. The method also includes sending an instruction to the communication bridge to initiate a communication connection to the destination address.

FIG. 1 illustrates a first embodiment of a system to make a call. The system is designated generally 100. The system 100 includes a user 102 having a mobile communication device 104. The mobile communication device 104 is adapted to communicate via wireless communication system 106. The wireless communication system 106 can communicate with a server system 108. While a single server system 108 is illustrated, the term “system” includes any collection of systems or sub-systems that individually or jointly execute a set, or multiple sets, of instructions to perform one or more of the functions described herein. The server system 108 can bridge communications between the wireless communication system 106 and a communication network 120. The communication network 120 enables Internet Protocol (IP) communication with a user device, such as computer 126, wireless communication device 124 or wired communication device 128 associated with a second user 122. The communication network 120 can also include one or more additional bridge systems to convert data received from the mobile communication device 104 to another communication protocol, such as IP communication and to transmit the communication over a communication network, such as a Public Switched Telephone Network (PSTN).

The server system 108 includes an access interface 110 to facilitate communication with the wireless communication system 106. The access interface 110 is adapted to receive a call to a communication address associated with the access interface 110. For example, the call can be initiated by the mobile communication device 104 in response to an automatic determination at the mobile communication device 104 to route the call via the access interface 110. To illustrate, the mobile communication device 104 may automatically determine to route a call as a Voice over Internet Protocol (VoIP) call based on an evaluation of a destination address received at the mobile communication device.

The server system 108 also includes logic 112 and memory 114 accessible to the logic 112. The memory 114 includes a plurality of modules 116-118 that are executable by the logic 112 to implement various functions of the server system 108. The modules 116-118 can be implemented in hardware, software or any combination thereof.

In a particular embodiment, the memory 114 can include a communication bridge 116, such as a VoIP telephony bridge. The VoIP telephony bridge 116 can be executed by the logic 112 to receive a call via the mobile communication system 106 and to communicate with a second device, such as a user device associated with the second user 122, based on the call. For example, where the communication bridge 116 includes a VoIP telephony bridge, the VoIP telephony bridge is adapted to receive a destination communication address from the module communication device 104, to initiate a call to the destination communication address and to convert voice call data received from the mobile communication device 104 to a VoIP call for transmission to the destination communication address. For example, the VoIP telephony bridge may convert signals received from the mobile communication device 104 in a mobile telephony protocol into VoIP signals for transmission to the destination communication address, and convert VoIP signals received from the destination communication address to mobile telephony protocol signals for transmission to the mobile communication device 104. In a particular embodiment, the communication bridge 116 may be adapted to facilitate non-voice data communications between the mobile communication device 104 and a device associated with the destination address (e.g., the computer 126, the wireless communication device 124, the wired communication device 128, or another communication device). For example, after the communication bridge 116 has established a communication link between the mobile communication device and a second device (i.e., a device associated with the destination address), the mobile communication device 104 may access data stored at the second device, the second device can send data to the mobile communication device, or both. The data can include voice or non-voice data. For example, the data can include multimedia data, text data, graphics data, and so forth. To illustrate a few non-limiting examples, the data can include contact list information, photographs, videos, executable program applications, web pages, or any other type of information.

The memory can also include an accounting module 118. The accounting module 118 can authenticate the mobile communication device 104 based on authentication information received from the mobile communication device 104. For example, the mobile communication device 104 can send authentication information validating that the mobile communication device 104 is authorized to send calls via the server system 108 using the communication bridge 116. In a particular embodiment, a user access telephone number can be associated with a user account record accessible to the accounting module 118. When a call is received at the server system 108 via the user access telephone number, the accounting module 118 can compare caller identification information associated with the call to an authorized telephone record of the user account record. If the caller identification information is associated with an authorized telephone that is related to the user access telephone number, the call is authenticated and the communication bridge 116 is invoked to bridge the call to the destination communication address.

FIG. 2 illustrates a second particular embodiment of a system to make a call. The system includes a mobile communication device 202. The mobile communication device 202 includes an antenna 204 adapted to send and receive wireless communications signals using a wireless communication protocol. The mobile communication device 202 also includes a display 206, and an input device 208. The input device 208 is adapted to receive input indicating a destination communication address, such as a telephone number, a Short Messaging Service (SMS) address, a web site address, etc. The input device can include a microphone, a keypad, a touch screen, one or more soft buttons, other input devices, or any combination thereof.

The mobile communication device 202 also includes logic 210 and memory 212 accessible to the logic 210. In a particular embodiment, mobile communication device 202 includes a computer-readable medium in which one or more sets of instructions, e.g. software, can be embedded. The instructions may embody one or more of the methods or logic as described herein. In a particular embodiment, the instructions may reside completely, or at least partially, within the memory 212, another memory (not shown), and/or within the logic 210. For example, the memory 212 can include one or more modules adapted to implement various functions of the mobile communication device 202. The modules can be implemented in hardware, software, or any combination thereof. For example, the memory 212 can include one or more software applications which, when executed by the logic 210, implement the functions of the one or more modules. In an alternative embodiment, dedicated hardware implementations, such as application specific integrated circuits, programmable logic arrays and other hardware devices, can be constructed to implement one or more of the methods described herein. Accordingly, the system encompasses software, firmware, and hardware implementations.

The mobile communication device 202 also includes an address analysis module 216. The address analysis module 216 is adapted to determine whether a destination communication address received at the mobile communication address 202 is of a predetermined type. In a particular embodiment, the predetermined type of destination address may be determined based on user configuration settings. For example, the user configurations settings may indicate that the predetermined type of destination address includes international telephony addresses, long distance telephony addresses, local telephony addresses, other telephony addresses, an Internet address, a Universal Resource Identifier (URI) address, an electronic messaging address (e.g., an SMS, Multimedia Messaging service (MMS), or email address), or any combination thereof. In a particular embodiment, the address analysis module 216 analyzes alpha-numerical digits of the destination communication address to determine whether the destination communication address is of the predetermined type. In another particular embodiment, the address analysis module 216 compares the destination communication address to one or more destination communication address patterns. The destination communication address patterns can include features that indicate that a call is of a particular type. For example the destination communication address patterns can identify international calls based on the number of digits in the destination communication address. In another example, the destination communication address patterns can identify long-distance calls based on the presence of an area code or the presence of a particular area code in the destination communication address. In still another example, the destination communication address patterns can identify an electronic messaging address or Internet address based on the presence of a URI scheme (e.g., http, mailto, ftp, etc.), or based on other syntax or semantics indicating that the destination communication address is a URI.

The mobile communication device 202 can also include a call module 214. The call module 214 can be adapted to initiate a call to a communication bridge when the destination communication address is of the predetermined type. The call module 214 can also send an instruction to the communication bridge to initiate or route a communication to the destination communication address. In a particular embodiment, the communication bridge includes a Voice over Internet Protocol (VoIP) telephony bridge, and the call module 214 is also adapted to send voice communication data to the VoIP telephony bridge to be converted to VoIP data for communication to the destination address. For example, the call module 214 can communicate with the VoIP telephony bridge using a wireless communication protocol.

The call module 214 can also be adapted to access non-voice data via the communication bridge. For example, the call module may receive non-voice data from a device associated with the destination address after a communication link to the destination address has been established. The call module 214 may be adapted to receive the data, and store the data in the memory 212 for access by another portion of the mobile communication device 202. For example, the call module 214 may receive image data via the communication bridge and store the image data at the memory 212 where the image data can be accessed by an image viewer element (not shown) of the mobile communication device 202. In another example, the call module 214 may receive contact list data via the communication bridge and store the contact list data at the memory 212 where the contact list data can be accessed by an address book manager element (not shown) of the mobile communication device 202.

FIG. 3 illustrates a first particular embodiment of a method of making a call. The method is designated generally 300. The method 300 includes, at 302, receiving input indicating a destination communication address at a mobile communication device. For example, the input can include a series of digits entered via a keypad of the mobile communication device, input selecting a communication address from a memory (e.g., from a contact list or speed dial list), a voice input, any other input indicating a destination address, or any combination thereof.

The method 300 also includes, at 304, determining whether the destination communication address is of a predetermined type 308. The method 300 can include accessing user configuration data 306 to determine which types of calls are of the predetermined type(s) 308. The user configuration data 306 can include information defining the predetermined type(s) 308 of destination communication addresses. For example, the predetermined types 308 may include international calls, long-distance calls, local calls, other types of telephony calls, a Universal Resource Identifier (URI), a network address, an electronic messaging address, or any combination thereof. In another particular embodiment, the user configuration data 306 can include one or more destination communication address patterns 310. For example, the destination communication address patterns 310 can include information sufficient to identify a particular type of call, such as an international call or long-distance call. To illustrate, the destination communication address patterns can indicate that calls that include an international calling code are of the predetermined type. In another example, the destination communication address patterns can indicate that calls that include particular area codes are of the predetermined type. Whether the destination communication address of a call is of a predetermined type can also be determined by analyzing alpha-numerical digits of the destination communication address.

When the destination communication address is of the predetermined type, the method 300 includes, at 314, initiating a call to a communication bridge via a mobile communication network. The method 300 also includes, at 316, sending authentication information to the communication bridge via the mobile communication network. For example, the authentication information can include caller identification information. In another example, the authentication information can include a key or other authentication data stored in a memory of the mobile communication device. The method further includes, at 318, sending an instruction to the communication bridge to initiate a communication connection to the destination communication address. When the communication connection has been established, the communication bridge may convert communication data received from the mobile communication device in a first communication protocol (e.g., a mobile communication protocol) to a second communication protocol for communication to the destination communication address. Similarly, the communication bridge can convert communication data received from the destination communication address in the second protocol to the first protocol for transmission to the mobile communication device.

When the destination communication address is not of the predetermined type, the method 300 includes, at 312, initiating a call to the destination communication address via the mobile communication network. For example, the call can be connected to the destination communication address via a wireless communication network, a Public Switched Telephone Network (PSTN), or both.

In a particular embodiment, the method 300 allows a call to be placed to any destination communication address as a Voice over Internet Protocol (VoIP) call by routing the call through the communication bridge as a VoIP call. The method 300 does not require that a user dial a telephony address of the communication bridge to initiate a call via the communication bridge. Rather, the method 300 determines whether the call is to a particular type of destination address, and automatically calls the communication bridge when it is. The destination communication address is passed to the communication bridge along with a command to initiate a communication connection to the destination communication address. The method 300 also does not require the user to enter an access code associated with the communication bridge to initiate communication via the communication bridge. Rather, the method 300 can automatically send authentication data from a memory of the mobile communication device to authenticate the mobile communication device to use the communication bridge.

FIG. 4 illustrates a first embodiment of a user interface for making a call. The user interface is designated generally 400. The user interface 400 includes a user selectable element 402 that allows a user to generate a user account to provide access to a communication bridge. The user interface 400 also includes information about a service providing access to the communication bridge for making calls.

FIG. 5 is a diagram of a second embodiment of a user interface for making a call. The user interface is designated generally 500. The user interface 500 includes a user input element 504 to allow a user to input a telephone number to be associated with a user account that is authorized to communicate via a communication bridge. The telephone number provided can be used to authenticate the telephone by comparing the provided telephone number to caller identification information received when the telephone calls the communication bridge. The user interface 500 also includes a user selectable element 502 that allows the user to enable or disable access to the communication bridge. The user interface 500 also includes a user selectable element 506 to save changes that have been made via the user interface 500.

FIG. 6 is a diagram of a third embodiment of a user interface for making a call. The user interface is designated generally 600. The user interface 600 includes user input element(s) 602 to receive input indicating a user access telephone number associated with a communication bridge. The user access telephone number is an access number assigned to the user and associated with user's account. A call placed to the user access telephone number is received by the communication bridge or an associated server system. If the user is authorized to communicate via the communication bridge, the call to the communication bridge can be forwarded to a destination communication address via an appropriate communication protocol.

The user interface 600 also includes user input element(s) 604 to receive a telephone number associated with a telephone authorized to access the communication bridge. The telephone number associated with the authorized telephone can be used by the communication bridge or the associated server system to authenticate that a particular telephone is authorized to communicate via the communication bridge. The telephone number associated with the authorized telephone can also be used by the communication bridge or the associated server system to relate a call to a customer account for billing purposes. The user interface 600 also includes a user selectable element 606 that allows the user to save changes made via the user interface 600. For example, when the user selectable element 606 is selected, changes made via the user interface 600 can be used to update a customer account record.

A particular embodiment is illustrated by the MyGlobalTalk service available from i2 Telecom International, Inc. MyGlobalTalk places Internet telephony in the hands of cell phone users, independent of wireless carrier technology, handset manufacturer, or the type of wireless carrier voice/data plan involved. In addition, MyGlobalTalk is fully functional without local access to the Internet or proximity to an Internet “hotspot”. Users also need not wait for the availability of a dual-mode WiFi phone, because MyGlobalTalk provides the benefits of a dual-mode phone at a fraction of the cost using the customer's existing mobile handset.

MyGlobalTalk is compatible with SmartPhone handsets and with other application enabled handsets, such as Java-enabled handsets, standard landline phones, and other communication devices. The MyGlobalTalk service includes a MyGlobalTalk mobile application and a MyGlobalTalk branded web site, an exemplary embodiment of which is illustrated in FIGS. 4-6. The MyGlobalTalk service enables mobile users to access the Internet (e.g., for Internet telephony communications, electronic messaging, or web site access) in an “untethered” manner via their MyGlobalTalk enabled phone.

With MyGlobalTalk, users need not change their traditional dialing procedures—just enter a destination communication address (e.g., dial the destination phone number) and the system automatically utilizes the MyGlobalTalk communication bridge when appropriate. For example, cell phone users can use their cell phones for VoIP calling, without dialing access codes or making other changes to their normal dialing procedure. Additionally, users can designate when calls should be placed as VoIP calls. This allows the same handset to automatically place some calls as regular telephone calls and some as VoIP calls based on user specified settings.

To initially access the MyGlobalTalk service, users send a message, such as an SMS message, using a designated Common Short Code with an associated keyword. The user then receives a message that includes a link for downloading the MyGlobalTalk mobile application or widget. The user then clicks on the link and the application is downloaded to his/her mobile handset. Once the application has been downloaded, the user launches it for subsequent installation and setup. When prompted by an install script, the user enters a phone number that was selected at the time the user signed up for the MyGlobalTalk service (e.g., a user access telephone number). Also during the installation and setup, the user can “ENABLE” the application. (It is worth noting that analysis, to date, indicates that only minimal battery drain is experienced while the MyGlobalTalk application is ENABLED). Once these steps are complete, the user is finished with the setup phase, and the user can begin using the MyGlobalTalk service.

Users can seamlessly dial international long distance calls without needing to enter any extra digits—just dial as one would normally dial an international number on a land-line phone. Other options can be available to the user as well, such as:

1) Selectively using MyGlobalTalk for:

-   -   i. International calling     -   ii. Domestic calling     -   iii. Domestic long-distance calling     -   iv. International & Domestic calling     -   v. All Calling     -   vi. Internet browsing and access     -   vii. Electronic messaging     -   viii. Other communications or combinations of the above;

2) MyGlobalTalk presence to detect a user's availability via the service;

3) MyGlobalTalk buddy lists;

4) MyGlobalTalk friends and family for account sharing;

5) MyGlobalTalk Party Line for conference calling;

6) MyGlobalTalk hide-n-seek for in-bound communications parsing or screening;

7) MyGlobalTalk neighborhood dialing for no cost communications when dialing from one MyGlobalTalk number to another MyGlobalTalk number;

8) MyGlobalTalk speed dials to input particular predefined communication address with a single click; and

9) MyGlobalTalk v-bridge to direct dial VoIP users associated with other VoIP service providers, e.g., Skype, or GoogleTalk.

10) MyGlobalTalk Real-Time for real-time or prompt feedback to user regarding the cost of a communication in progress or just completed

One feature of MyGlobalTalk relates to how the service takes advantage of the particular services offered by certain wireless carriers. While MyGlobalTalk offers customers significant cost savings and is very easy to use, there are a number of carriers with certain branded features that, when coupled with MyGlobalTalk, can substantially reduce the cost of these cellular plans. For example, many wireless carriers allow free calls to be made to certain preselected telephone numbers. Examples includes T-Mobile's “myFaves” service, Sprint's “Sprint-to-Home” service, AllTel's “myCircle” service, and so forth.

A user may designate his or her MyGlobalTalk phone number (e.g., his or her user access number) as a preselected free calling number, e.g., a “home” or “favorite” number. To illustrate, with T-Mobile's myFaves service users can designate up to five (5) “favorite” numbers, with Sprint's Sprint-to-Home service users can designate a single number, or with AllTel's myCircle service users can designate up to ten (10) numbers. In each case, if a MyGlobalTalk user designates his or her MyGlobalTalk phone number as one of the designated numbers, then when the MyGlobalTalk application is enabled and a call is automatically routed to the MyGlobalTalk communication bridge, the call does not subtract minutes from the cell phone calling plan. The savings for business travelers, students, military users, ex-patriates, etc., who need to make frequent international calls, can be very substantial. With MyGlobalTalk, these users can complete these calls from their mobile handsets without being charged per minute fees or using an allocation of free or prepaid minutes. By enabling the MyGlobalTalk feature for all international calls plus domestic calls, or selecting the “All Calls” option, all of the user's calls can be completed without ever touching the user's cellular calling plan minutes. This will allow users to sign up for the minimum-cost plans offered by wireless carriers and yet still be able to make an unlimited number of international and domestic long-distance calls.

MyGlobalTalk is simple to use and, once activated, does not require further adjustments. The Download and Setup process utilizes standard SMS text messaging for acquiring the application and two simple data entry points during installation and setup.

FIG. 7 illustrates a particular embodiment of a method of downloading an application to enable a communication device to automatically route telephone calls via a communication bridge, such as the MyGlobalTalk application, the method designated generally 700. The method 700 includes, at 702, using a communication device, such as a mobile handset, to send a message to the designated CSC (Common Short Code). For example, the message may include the keyword “MyGlobalTalk” in the subject line or body of the message. The MyGlobalTalk service system may send a response to the mobile handset. The response can include a link that, when activated, connects the mobile handset to a download server. The method 700 also includes, at 704, receiving the link and selecting the link to accept the licensing agreement and begin the download. The method 700 also includes, at 706, receiving the download. For example, the download can include a MyGlobalTalk application or an installation application or script that installs the MyGlobalTalk application. The method 700 further includes, at 708, installing and configuring the MyGlobalTalk application on the mobile handset.

FIG. 8 illustrates a particular embodiment of a method of downloading an application to automatically route calls to a communication bridge, such as the MyGlobalTalk application. The method is designated generally 800. The method 800 includes, at 802, selecting the MyGlobalTalk installation application to begin the installation. For example, the user may find the application in a memory of the mobile handset and click (or double-click) on the application to begin the installation process. The method 800 also includes, at 804, entering a phone number that was selected during the MyGlobalTalk account signup process (e.g., a telephone number associated with the mobile handset and/or a user access number). The method 800 also includes, at 806, selecting to enable the MyGlobalTalk application.

FIG. 9 illustrates a particular embodiment of a method of setting up a user account to access a communication bridge, such as a MyGlobalTalk account. The method is designated generally 900. The method 900 includes, at 902, accessing a user account associated with the MyGlobalTalk service. For example, the user may log into an online account using a User Name and Password associated with the user's MyGlobalTalk service account. The method 900 also includes, at 904, selecting the MyGlobalTalk account options. The method 900 also includes, at 906, entering the communication address (e.g., a phone number) associated with the mobile handset (or other communication device) a user plans to use with the MyGlobalTalk service. The method 900 further includes, at 908, changing the MyGlobalTalk status to enabled. The method 900 also includes, at 910, saving the changes to the MyGlobalTalk account. For example, the user may select a “submit” option. After the account set up process is complete, the MyGlobalTalk service is ready for use.

To use the MyGlobalTalk service, a user inputs a destination communication address (e.g., dials a telephone number as normal). The MyGlobalTalk application running on the user's mobile handset determines proper call routing based on the set-up options. In addition, MyGlobalTalk permits multiple methods of receiving the destination communication address, including: 1) Keypad, 2) Contacts, and 3) Call History. In each case, the MyGlobalTalk application analyzes the destination communication address and routes the call according to the user's set up parameters. The MyGlobalTalk application also remembers its users, and whenever an update, new feature, or newer version of the application becomes available, the users can receive a notification on their handset with instructions on how to acquire the updates. The MyGlobalTalk mobile application and updates are available to the users, regardless of which mobile communication service provider they use.

The present disclosure contemplates a computer-readable medium that includes instructions or receives and executes instructions responsive to a propagated signal, so that a device connected to a network can communicate voice, video or data over the network. Further, the instructions may be transmitted or received over the network via the network interface device. The term “computer-readable medium” includes a single medium or multiple media, such as a centralized or distributed database, and/or associated caches and servers that store one or more sets of instructions. The term “computer-readable medium” includes any medium that is capable of storing, encoding or otherwise tangibly embodying a set of instructions for execution by a processor or that cause a computer system to perform any one or more of the methods or operations disclosed herein.

In a particular non-limiting, exemplary embodiment, the computer-readable medium can include a solid-state memory such as a memory card, SIM card or other package that houses one or more non-volatile read-only memories. Further, the computer-readable medium can be a random access memory or other volatile re-writable memory. Additionally, the computer-readable medium can include a magneto-optical or optical medium, such as a disk or tapes or other storage device to capture carrier wave signals such as a signal communicated over a transmission medium. A digital file attachment to an e-mail or other self-contained information archive or set of archives may be considered a distribution medium that is equivalent to a tangible storage medium. Accordingly, the disclosure is considered to include any one or more of a computer-readable medium or a distribution medium and other equivalents and successor media, in which data or instructions may be stored.

Although the present specification describes components and functions that may be implemented in particular embodiments with reference to particular standards and protocols, the disclosed embodiments are not limited to such standards and protocols. For example, standards for Internet and other packet switched network transmission (e.g., TCP/IP, UDP/IP, HTML, HTTP) represent examples of the state of the art. Such standards are periodically superseded by faster or more efficient equivalents having essentially the same functions. Accordingly, replacement standards and protocols having the same or similar functions as those disclosed herein are considered equivalents thereof.

The illustrations of the embodiments described herein are intended to provide a general understanding of the structure of the various embodiments. The illustrations are not intended to serve as a complete description of all of the elements and features of apparatus and systems that utilize the structures or methods described herein. Many other embodiments may be apparent to those of skill in the art upon reviewing the disclosure. Other embodiments may be utilized and derived from the disclosure, such that structural and logical substitutions and changes may be made without departing from the scope of the disclosure. Additionally, the illustrations are merely representational and may not be drawn to scale. Certain proportions within the illustrations may be exaggerated, while other proportions may be reduced. Accordingly, the disclosure and the figures are to be regarded as illustrative rather than restrictive.

One or more embodiments of the disclosure may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any particular invention or inventive concept. Moreover, although specific embodiments have been illustrated and described herein, it should be appreciated that any subsequent arrangement designed to achieve the same or similar purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all subsequent adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the description.

The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1.72(b) and is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, various features may be grouped together or described in a single embodiment for the purpose of streamlining the disclosure. This disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter may be directed to less than all of the features of any of the disclosed embodiments. Thus, the following claims are incorporated into the Detailed Description, with each claim standing on its own as defining separately claimed subject matter.

The above-disclosed subject matter is to be considered illustrative, and not restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments, which fall within the true spirit and scope of the present invention. Thus, to the maximum extent allowed by law, the scope of the present invention is to be determined by the broadest permissible interpretation of the following claims and their equivalents, and shall not be restricted or limited by the foregoing detailed description. 

1. A method, comprising: receiving, at a mobile communication device, input indicating a destination address; determining whether the destination address is of a predetermined type; and when the destination address is of the predetermined type, initiating a call to a communication bridge via a mobile communication network and sending an instruction to the communication bridge to initiate a communication connection to the destination address.
 2. The method of claim 1, further comprising, when the destination address is not of the predetermined type, initiating a communication to the destination address via the mobile communication network.
 3. The method of claim 1, further comprising sending authentication information to the communication bridge via the mobile communication network.
 4. The method of claim 3, wherein the authentication information comprises caller identification information.
 5. The method of claim 3, wherein authentication information is not received from a user at the mobile communication device.
 6. The method of claim 1, wherein determining whether the destination address is of a predetermined type comprises analyzing alpha-numerical digits of the destination address.
 7. The method of claim 1, wherein the predetermined type comprises an international telephony address.
 8. The method of claim 1, wherein the predetermined type comprises a long-distance telephony address.
 9. The method of claim 1, wherein the predetermined type comprises an internet address.
 10. The method of claim 1, wherein determining whether the destination address is of a predetermined type comprises comparing the destination address to a destination address pattern.
 11. The method of claim 1, wherein determining whether the destination address is of a predetermined type comprises accessing user configuration data to determine the predetermined type.
 12. The method of claim 1, wherein a user does not dial a telephony address of the communication bridge to initiate the call to the communication bridge.
 13. The method of claim 1, wherein a user does not enter an access code associated with the communication bridge to initiate the communication to the destination communication address.
 14. A processor-readable medium, comprising: instructions that, when executed by a processor, cause the processor to receive input indicating a destination address; instructions that, when executed by the processor, cause the processor to determine whether the destination address is of a predetermined type; instructions that, when executed by the processor, cause the processor to initiate a call to a communication bridge via a mobile communication network when the destination address is of the predetermined type; and instructions that, when executed by the processor, cause the processor to send an instruction to the communication bridge to initiate a communication to the destination address.
 15. The processor-readable medium of claim 14, wherein the instructions are adapted to be executed by a processor of a mobile communication device.
 16. The processor-readable medium of claim 14, wherein the communication bridge comprises a Voice over Internet Protocol (VoIP) telephony bridge, and wherein the communication comprises a VoIP call.
 17. The processor-readable medium of claim 14, further comprising, instructions that when executed by the processor, cause the processor to receive data from a device associated with the destination address via the communication bridge after communication to the destination address is initiated.
 18. The processor-readable medium of claim 14, wherein the data comprises voice data.
 19. The processor-readable medium of claim 14, wherein the data comprises non-voice data.
 20. A mobile communication device, comprising: an input device to receive input indicating a destination communication address; an address analysis module to determine whether the destination communication address is of a predetermined type; and a call module to initiate a call to a communication bridge when the destination communication address is of the predetermined type and to send an instruction to the communication bridge to initiate a communication connection to the destination communication address.
 21. The mobile communication device of claim 20, wherein the call module is further adapted to send voice communication data to the VoIP telephony bridge to be converted to VoIP data to communicate to the destination communication address.
 22. The mobile communication device of claim 20, wherein the address analysis module is configured to alpha-numeric digits of the destination communication address to determine whether the destination communication address is of the predetermined type.
 23. A system, comprising: an access interface to receive a call to a telephony address associated with the access interface, wherein the call is initiated by a mobile communication device in response to an automatic determination at the mobile communication device to route the call via the access interface based on a destination communication address received at the mobile communication device; and a communication bridge to initiate a communication to the destination communication address and to convert data received via the call to an alternate communication protocol for communication to the destination communication address.
 24. The system of claim 23, further comprising an accounting module to authenticate the mobile communication device based on authentication information received from the mobile communication device. 